Configuring scriptset directories and files
Use the
Configure tab screen to create, modify and delete scriptsets.
Before you can run a load process, you need to configure the directories and file names of your scriptsets.
Procedure
- Click the
Configure
tab.
- If you want to modify an existing configuration, click the
Scriptsets menu in the toolbar and select the scriptset you want to modify. If you want to create a new configuration, click the
New Config button and enter the name of the new configuration in the
Script Set Name field.
- Click the
Create Directory Structure icon and select the location for this configuration's directories. You only need to select the root file, iLoader automatically enters the scriptset name as the directory. A brief explanation of each directory is given in the table below.
| Data Load Repository |
The full path to the directory where the raw data files for import are located.
|
| Data Backup Repository
|
The full path to the directory where the database is backed up.
|
| Decode File Repository
|
The full path to the directory where the decode files are held. These files are referenced by the Data Transformation data script file and are used to build remaps on the database.
|
| Report Repository
|
The full path to the directory where the reports are located, for each load an import report is created and placed in this directory.
|
| Script File Location |
The full path to the directory where the Control File and other script files are stored.
|
| Success/Failure File Location |
The full path to the directory where the system writes files containing information on the success or failure of a load process.
|
- Click the
Create Default Files icon to automatically populate the script file fields with default names. If required, you can change any file name from the default. The five iLoader default script names are described in the table below.
| Control File |
Automatically inserted as
Control.txt. It is the first script to be parsed and contains a series of configuration statements. This script can also be used to load tables.
|
| Data Transformation Script File |
Automatically inserted as
Datatrans.txt. Encompasses full iLoader functionality.
|
| Preload Script File |
Automatically inserted as
Preload.txt. Was used for preload stages such as dropping objects and moving files. You should now use the
Datatrans.txt script to specify these stages.
|
| Link Script File |
Automatically inserted as
Linkscript.txt. Was used for creating links between table columns. You should now use the
Datatrans.txt script to specify links.
|
| PostLoad Script File |
Automatically inserted as
PostLoad.txt. Was used for post load processing, such as data audit. You should now use the
Datatrans.txt script to specify post load processing.
|
- When iLoader logs in to Engine, it will always be as the SYSTEM user. It may be that the password for this user needs to be changed for security reasons. If this is the case, it must be supplied in the
Engine Password field as part of the configuration. This password is stored in an encrypted form in the
Config.XML file.
- Click the
Save Config button to save your changes.
Results
The scriptset will be created in the project's directory, in a folder with the name of the scriptset you specified in the
Script Set Name field.
|
|
